Out-of-bounds read in code handling HTTP/2 trailers :

libcurl contains an out bounds read in code handling HTTP/2 trailers.
It was reported (https://github.com/curl/curl/pull/2231) that reading an HTTP/2 trailer could mess up future trailers since the stored size was one byte less than required. The problem is that the code that creates HTTP/1-like headers from the HTTP/2 trailer data once appended a string like `:` to the target buffer, while this was recently changed to `: ` (a space was added after the colon) but the following math wasn't updated correspondingly. When accessed, the data is read out of bounds and causes either a crash or that the (too large) data gets passed to client write. This could lead to a denial-of-service situation or an information disclosure if someone has a service that echoes back or uses the trailers for something. (CVE-2018-1000005)

HTTP authentication leak in redirects :

libcurl might accidentally leak authentication data to third parties.
When asked to send custom headers in its HTTP requests, libcurl will send that set of headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the `Location:` response header value. Sending the same set of headers to subsequest hosts is in particular a problem for applications that pass on custom `Authorization:` headers, as this header often contains privacy sensitive information or data that could allow others to impersonate the libcurl-using client's request. (CVE-2018-1000007)

New curl packages are available for Slackware 14.0, 14.1, 14.2, and
-current to fix security issues.

- http2: fix incorrect trailer buffer size   (CVE-2018-1000005)

- http: prevent custom Authorization headers in redirects   (CVE-2018-1000007)

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

It was discovered that curl incorrectly handled certain data. An attacker could possibly use this to cause a denial of service or even to get access to sensitive data. This issue only affected Ubuntu 16.04 LTS and Ubuntu 17.10.

It was discovered that curl could accidentally leak authentication data. An attacker could possibly use this to get access to sensitive information. (CVE-2018-1000007).

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Two vulnerabilities were discovered in cURL, an URL transfer library.

  - CVE-2018-1000005     Zhouyihai Ding discovered an out-of-bounds read in the     code handling HTTP/2 trailers. This issue doesn't affect     the oldstable distribution (jessie).

  - CVE-2018-1000007     Craig de Stigter discovered that authentication data     might be leaked to third parties when following HTTP     redirects.

HTTP authentication leak in redirects

libcurl might accidentally leak authentication data to third parties.
When asked to send custom headers in its HTTP requests, libcurl will send that set of headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the `Location:` response header value. Sending the same set of headers to subsequest hosts is in particular a problem for applications that pass on custom `Authorization:` headers, as this header often contains privacy sensitive information or data that could allow others to impersonate the libcurl-using client's request. (CVE-2018-1000007)

Out-of-bounds read in code handling HTTP/2 trailers

libcurl contains an out bounds read in code handling HTTP/2 trailers.
It was reported (https://github.com/curl/curl/pull/2231) that reading an HTTP/2 trailer could mess up future trailers since the stored size was one byte less than required. The problem is that the code that creates HTTP/1-like headers from the HTTP/2 trailer data once appended a string like `:` to the target buffer, while this was recently changed to `: ` (a space was added after the colon) but the following math wasn't updated correspondingly. When accessed, the data is read out of bounds and causes either a crash or that the (too large) data gets passed to client write. This could lead to a denial-of-service situation or an information disclosure if someone has a service that echoes back or uses the trailers for something. (CVE-2018-1000005)

The remote host is affected by the vulnerability described in GLSA-201804-04 (cURL: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in cURL. Please review the       CVE identifiers referenced below for details.
  Impact :

    Remote attackers could cause a Denial of Service condition, obtain       sensitive information, or have other unspecified impacts.
  Workaround :

    There is no known workaround at this time.

ID	Name	Product	Family	Published	Updated	Severity
106930	Amazon Linux AMI : curl (ALAS-2018-951)	Nessus	Amazon Linux Local Security Checks	2/22/2018	4/18/2018	critical
106309	Slackware 14.0 / 14.1 / 14.2 / current : curl (SSA:2018-024-01)	Nessus	Slackware Local Security Checks	1/25/2018	2/20/2018	critical
106517	Fedora 26 : curl (2018-85655b12b6)	Nessus	Fedora Local Security Checks	1/31/2018	1/6/2021	critical
106510	Fedora 27 : curl (2018-241a5a2409)	Nessus	Fedora Local Security Checks	1/31/2018	1/6/2021	critical
106558	Ubuntu 14.04 LTS / 16.04 LTS : curl vulnerabilities (USN-3554-1)	Nessus	Ubuntu Local Security Checks	2/1/2018	10/20/2023	critical
106412	Debian DSA-4098-1 : curl - security update	Nessus	Debian Local Security Checks	1/29/2018	11/13/2018	critical
109122	Amazon Linux 2 : curl (ALAS-2018-951)	Nessus	Amazon Linux Local Security Checks	4/18/2018	4/18/2018	critical
108925	GLSA-201804-04 : cURL: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	4/10/2018	6/7/2018	critical

Detections

Analytics

Plugins Search

critical

critical

critical

critical

critical

critical

critical

critical